The system command node includes the following subnode commands:
auditlogs
bootimages
crashdumps
hardware
raidsets
rootfilesystem
software
Each of the subnode commands, and the leaf-node commands attached to them, is described in detail, with parameters and arguments listed for each command.
Examples of command usage are included in the discussions.
CLI:
system auditlogs save -logid log_ID -ftpurl upload_file_URL
GUI: Navigate to the System → Audit Logs node. To save a specific audit log entry, select it from the table and run the Save Audit Logs command from the drop-down menu of the action pane. Enter the appropriate information in the Upload File URL field and click Save Audit Logs.
The system auditlogs save command saves an audit log entry to a specified FTP URL. This is useful if you need to send audit log entries to Network Appliance Technical Support.
-logid log_ID
This specifies the ID of the log entry to be saved.
-ftpurl upload_file_URL
This specifies the URL where the audit log is to be saved.
The following example saves audit log entry 150 at the URL ftp://example.com/tmp/spinserverlogs/log150:
spinserver::> system auditlogs save -logid 150 -ftpurl ftp://example.com/tmp/spinserverlogs/log150
CLI:
system auditlogs show [-logid log_ID]
GUI: Navigate to the System → Audit Logs node. To display a specific audit log entry, select it from the table and run the Show command from the drop-down menu of the action pane.
The system auditlogs show command displays information about all audit log entries or information about a specific entry. Use the command with the -logid parameter to display specific information for an entry, or without the parameter to display information about all entries. The information includes the following:
The log ID
The SpinServer ID
The IP address from which the command was issued
The user who issued the command
The command that was issued
The date and time at which the command was issued
Result of the command (success or failure)
Error message, if any
Note: Use the cluster properties modify command to set the number of entries in the audit log. The default number of entries is 2,000. When the audit log reaches the permitted number of entries, it deletes the oldest entries as new entries are made.
The following example displays all audit log entries:
spinserver::> system auditlogs show
Log SpinServer ID Command Path Date
ID
1 Server1 raid subsystems show 10/7/02 8:45:30 AM EST
2 Server1 spinservers show 10/7/02 8:45:37 AM EST
3 Server1 ports show 10/7/02 8:45:38 AM EST
4 Server1 ports show 10/7/02 8:45:40 AM EST
5 Server1 cluster show 10/7/02 8:45:40 AM EST
6 Server1 storage units show 10/7/02 8:45:43 AM EST
7 Server1 filestorage scheduler task show 10/7/02 8:46:07 AM EST
8 Server1 filestorage scheduler schedule show 10/7/02 8:46:08 AM EST
9 Server1 filestorage scheduler job show 10/7/02 8:46:10 AM EST
-- Type 'q' to quit and any key to continue --
The following example displays information about log entry 150:
spinserver::> system auditlogs show -logid 150 Log ID 150 SpinServer ID Server1 IP Address 10.1.1.150 User root Command Path filestorage scheduler task show Command filestorage scheduler task show Date 10/9/02 8:32:07 AM EST Result Success Error Message
The system bootimages subnode provides the following commands for working with SpinServer startup images:
setdefault
show
CLI:
system bootimages setdefault -ssid spinserver -label boot_image
GUI: Navigate to the System → Boot Images node, then select the appropriate startup image from the table and run the Set As Default Boot Image command from the drop-down menu of the action pane.
The system bootimages setdefault command sets the default startup image for a SpinServer. Each SpinServer has two startup images; toggling between them is useful when upgrading the SpinFS software.
-ssid spinserver
This specifies the SpinServer whose startup image is to be changed.
-label boot_image
This specifies the startup image to be used. Possible values are image1 and image2.
The following example sets the default startup image to image2 on the SpinServer named Server1:
spinserver::> system bootimages setdefault -ssid Server1 -label image2
CLI:
system bootimages show [-ssid spinserver -label boot_image]
GUI: Navigate to the System → Boot Images node. To display information about a specific startup image, select it from the table and run the Show command from the drop-down menu of the action pane.
The system bootimages show command displays information about a SpinServer's startup images. Run the command without any parameters to display the following information about both startup images:
SpinServer ID
Label
Path
Device
Current status
Default status
Run the command with the -ssid and -label parameters for a specific startup image to additionally display the image's kernel options.
[-ssid spinserver]
This specifies the SpinServer whose startup-image information is to be displayed.
[-label boot_image]
This specifies the startup image about which information is to be displayed. Possible values are image1 and image2.
The following example displays information about all startup images on a SpinServer cluster:
spinserver::> system bootimages show
SpinServer ID Label Path Device Current Default
Server1 image1 /boot/vmlinuz /dev/sda2 false false
Server1 image2 /boot/vmlinuz /dev/sda2 true true
The following example displays information about the startup image named image2 on the SpinServer named Server1:
spinserver::> system bootimages show -ssid Server1 -label image2 SpinServer ID Server1 Label image2 Path /boot/vmlinuz Device /dev/sda2 Kernel Options "console=ttyS0,115200n8 apm=power-off" Current true Default true
CLI:
system crashdumps delete -ssid spinserver -name file_name
GUI: Navigate to the System → Kernel Crash Dumps node, then select the appropriate crash file from the table and run the Delete command from the drop-down menu of the action pane.
The system crashdumps delete command deletes a crash file. Crash files are used by Technical Support to analyze software failures.
Note: Do not delete a crash file unless directed to do so by Technical Support personnel.
-ssid spinserver
This specifies the SpinServer on which the crash file is located.
-name file_name
This specifies the crash file to be deleted.
The following example deletes a crash file named vmdump.1 on a SpinServer named Server1:
spinserver::> system crashdumps delete -ssid Server1 -name vmdump.1
CLI:
system crashdumps show [-ssid spinserver -name file_name]
GUI: Navigate to the System → Kernel Crash Dumps node. To display information about a specific crash file, select it from the table and run the Show command from the drop-down menu of the action pane.
The system crashdumps show command displays information about a crash file. Crash files are used by Technical Support to analyze software failures.
[-ssid spinserver]
This specifies the SpinServer on which the crash file is located.
[-name file_name]
This specifies the crash file to be deleted.
The following example displays information about a crash file named vmdump.1 on the SpinServer named Server1:
spinserver::> system crashdumps show -ssid Server1 -name vmdump.1 SpinServer ID Server1 FileName vmdump.1 Build 35372 Creation Date 1/14/03 11:34:11 AM EST Size 1077510144 Last Modified 1/14/03 11:35:29 AM EST Readable true Writeable true Compression Method Not Compressed Encryption Method Not Encrypted
The system hardware fibrechannel leaf node provides the following commands for working with a SpinServer's Fibre Channel interfaces:
bringup
cardreset
lipreset
modify
setmode
show
takedown
CLI:
system hardware fibrechannel bringup -ssid spinserver -channel channel_number
GUI: Navigate to the System → Hardware → Fibre Channel node. Select a channel from the table and run the Bring channel up command from the drop-down menu of the action pane.
The system hardware fibrechannel bringup command brings up a specified Fibre Channel channel.
-ssid spinserver
This specifies the SpinServer on which the Fibre Channel is located.
-channel channel_number
This specifies the channel number that is to be brought up.
The following example brings up Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel bringup -ssid Server1 -channel 0
CLI:
system hardware fibrechannel cardreset -ssid spinserver -channel channel_number
GUI: Navigate to the System → Hardware → Fibre Channel node. Select a channel from the table and run the Card Reset command from the drop-down menu of the action pane.
The system hardware fibrechannel cardreset command resets the Fibre Channel card in a specified SpinServer.
-ssid spinserver
This specifies the SpinServer on which the Fibre Channel is located.
-channel channel_number
This specifies a channel number on the card that is to be reset.
The following example resets the Fibre Channel card with channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel cardreset -ssid Server1 -channel 0
CLI:
system hardware fibrechannel lipreset -ssid spinserver -channel channel_number
GUI: Navigate to the System → Hardware → Fibre Channel node. Select a channel from the table and run the Lip Reset command from the drop-down menu of the action pane.
The system hardware fibrechannel lipreset command issues a LIP reset to a specified Fibre Channel.
-ssid spinserver
This specifies the SpinServer on which the Fibre Channel is located.
-channel channel_number
This specifies the channel number to which the LIP reset is to be issued.
The following example issues a LIP reset to Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel lipreset -ssid Server1 -channel 0
CLI:
system hardware fibrechannel modify -ssid spinserver -channel channel_number -desiredrate data_rate
GUI: Navigate to the System → Hardware → Fibre Channel node. Select a channel from the table and run the Show command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then run the Modify command from the drop-down menu.
The system hardware fibrechannel modify command changes the data rate for a Fibre Channel port.
-ssid spinserver
This specifies the SpinServer on which the Fibre Channel is located.
-channel channel_number
This specifies the channel number that is to have its data rate changed.
-desiredrate data_rate
This specifies the new data rate for the channel. Possible values are 1GB for 1 Gb/s, 2GB for 2 Gb/s, and AUTO for automatic detection.
The following example changes the data rate to AUTO (automatic detection) for Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel modify -ssid Server1 -channel 0 -desiredrate AUTO
CLI:
system hardware fibrechannel setmode -ssid spinserver -channel channel_number -mode mode
GUI: Navigate to the System → Hardware → Fibre Channel node. Select a channel from the table and run the Set Channel Mode command from the drop-down menu of the action pane. Select the appropriate value from the drop-down menu that is displayed, then click the Set Channel Mode button.
The system hardware fibrechannel setmode command sets the mode for a Fibre Channel channel.
-ssid spinserver
This specifies the SpinServer on which the Fibre Channel is located.
-channel channel_number
This specifies the channel number that is to have its mode set.
-mode mode
This specifies the mode for the channel. Possible values are LoopOnly, LoopPreferred, PointToPointOnly, and PointToPointPreferred. The default is LoopPreferred.
The following example sets the mode to LoopOnly for Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel setmode -ssid Server1 -channel 0 -mode LoopOnly
CLI:
system hardware fibrechannel show [-ssid spinserver -channel channel_number]
GUI: Navigate to the System → Hardware → Fibre Channel node. To display information about a specific channel, select it from the table and run the Show command from the drop-down menu of the action pane.
The system hardware fibrechannel show command displays the following information about one or more Fibre Channel ports:
SpinServer ID
Channel number
Whether or not the channel is present
Port type (QL2200 or QL2312)
Topology (N_Port, NL_Port, F_Port, or FL_Port) (specific port only)
Node name
Port name
State of the channel (up or down)
Current data rate
Desired channel mode (LoopOnly, LoopPreferred, PointToPointOnly, or PointToPointPreferred) (specific port only)
[-ssid spinserver]
This specifies the SpinServer on which the Fibre Channel is located.
[-channel channel_number]
This specifies the channel number.
The following example displays information about Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel show -ssid Server1 -channel 0
SpinServer ID Server1
Channel 0
Present true
Port Type QL2200
Topology NL_Port
Node Name 200100e08b25fb27
Port Name 200100e08b25fb27
State Up
Current Data Rate 1GB
Desired Channel Mode LoopPreferred
CLI:
system hardware fibrechannel takedown -ssid spinserver -channel channel_number
GUI: Navigate to the System → Hardware → Fibre Channel node. Select a channel from the table and run the Bring channel up command from the drop-down menu of the action pane.
The system hardware fibrechannel takedown command takes down a specified Fibre Channel channel.
-ssid spinserver
This specifies the SpinServer on which the Fibre Channel is located.
-channel channel_number
This specifies the channel number that is to be brought up.
The following example takes down Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel takedown -ssid Server1 -channel 0
To display configuration information about VERITAS Netbackup DataCenter, 3.4 installed to be used with NDMP for a SpinServer, use the following system hardware tape commands:
drives show
robots show
CLI:
system hardware tape drives show [-devid device_ID]
GUI: Navigate to the System → Hardware → Tape → Tape Drives node. To display information about a specific tape drive, select it from the table and run the Show command from the drop-down menu of the action pane.
The system hardware tape drives show command displays the following information about the tape drives for the VERITAS Netbackup DataCenter, 3.4 installed to be used with NDMP Version 2.0 for a SpinServer system:
Device ID
World Wide name
Logical unit number (LUN)
Primary channel
Primary loop ID
Secondary channel
Secondary loop ID
Vendor name
Product name
Revision number
To obtain information about a specific tape drive, use the -devid parameter. To obtain information about all tape drives on the system, use the command without any parameters.
The following example displays information about a tape drive with a device ID of 1.
spinserver::> system hardware tape drives show -devid 1
CLI:
system hardware tape robots show [-devid device_ID]
GUI: Navigate to the System → Hardware → Tape → Tape Robots node. To display information about a specific tape robot, select it from the table and run the Show command from the drop-down menu of the action pane.
The system hardware tape robots show command displays the following information about the tape robots for the VERITAS Netbackup DataCenter, 3.4 installed to be used with NDMP Version 2.0 for a SpinServer system:
Device ID
World Wide name
Logical unit number (LUN)
Primary channel
Primary loop ID
Secondary channel
Secondary loop ID
Vendor name
Product name
Revision number
To obtain information about a specific tape drive, use the -devid parameter, as shown in the following example. To obtain information about all tape drives on the system, use the command without any parameters.
The following example displays information about a tape robot with a device ID of 1.
spinserver::> system hardware tape robots show -devid 1
Use the system raidsets show command to display information about the RAID sets on a SpinServer system.
CLI:
system raidsets show [-ssid spinserver -devid device_ID]
GUI: Navigate to the System → Raid Sets node. To display information about a specific RAID set, select it from the table and run the Show command from the drop-down menu of the action pane.
The system raidsets show command displays information about a SpinServer's internal RAID sets. Use the command without any parameters to display information about both RAID sets, or with the -ssid and -devid parameters to display information about a specified RAID set. The information for all RAID sets includes the following:
SpinServer ID
Device ID
Status
Whether or not the RAID set is read-only
Whether Disk0 is operational or faulty
Whether Disk1 is operational or faulty
Resynchronization status
Percentage of RAID set used
The display for a specific RAID set includes the following additional information:
Description
RAID level
Number of blocks
Number of disks
Number of operating disks
Disk0 name
Disk1 name
Whether a resynchronization is in progress
Mount path
Size, in MB
Available size, in MB
Used size, in MB
Percentage used
Note: This command applies only to the SpinServer's internal RAID sets. It does not apply to SpinStor RAID or JBOD disk enclosures that are externally connected to the SpinServer.
[-ssid spinserver]
This specifies the SpinServer.
[-devid device_ID]
This specifies the device ID of the RAID set.
The following example displays information about an internal RAID set named md1 on a SpinServer named Server1:
spinserver::> system raidsets show -ssid Server1 -devid md1 SpinServer ID Server1 Device ID md1 Description Internal RAID Set md1 RAID Level raid1 Status active Read Only false Blocks 1052160 Disks 2 Operating Disks 2 Disk0 Name sda2 Disk0 Operational true Disk0 Faulty false Disk1 Name sdb2 Disk1 Operational true Disk1 Faulty false Resync In Progress false Resync Status Mount Path
The system rootfilesystem subnode provides the following commands for working with the SpinServer's root file-system partitions:
modify
show
upgradesoftware
CLI:
system rootfilesystem modify -ssid spinserver -name file_system_name -synconreboot {NONE | CONFIGURATION | FILESYSTEM}
GUI: Navigate to the System → Root File System node, then select the appropriate root file system from the table and run the Show command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then run the Modify command from the drop-down menu.
The system rootfilesystem modify command sets the synchronization value for a SpinServer's root file system at the next system restart.
-ssid spinserver
This specifies SpinServer whose root file system is to be synchronized.
-name file_system_name
This specifies the root file-system partition on which the synchronization is to take place. Possible values are ROOT and ALTROOT.
-synconreboot {NONE | CONFIGURATION | FILESYSTEM}
This specifies the synchronization value for the root file system the next time the SpinServer is restarted. Possible values include NONE, for no synchronization; CONFIGURATION, for configuration synchronization; and FILESYSTEM, to synchronize the two root file systems.
After a system restart, this setting is automatically reset to NONE.
The following example modifies the root file-system partition named ROOT on a SpinServer named Server1 so that it synchronizes the configuration of the root file system the next time the SpinServer is restarted:
spinserver::> system rootfilesystem modify -ssid Server1 -name ROOT -synconreboot CONFIGURATION
CLI:
system rootfilesystem show [-ssid spinserver -name file_system_name]
GUI: Navigate to the System → Root File System node. To display information about a specific root file system, select it from the table and run the Show command from the drop-down menu of the action pane.
The system rootfilesystem show command displays information about a SpinServer's root file-system partitions. Use the command with the -ssid and -name parameters to display information about a specific partition, or with no parameters to display information about both partitions. The following information is displayed:
SpinServer ID
Partition name
Device
Mount path
Version
Build number
The display for a specific partition includes the following additional information:
Installation time
Time of last synchronization
Time of last configuration synchronization
[-ssid spinserver]
This specifies the SpinServer whose root file-system information is to be displayed.
[-name file_system_name]
This specifies the root file-system partition about which information is to be displayed.
The following example displays information about all root file-system partitions on a SpinServer:
spinserver::> system rootfilesystem show
SpinServer ID Name Device Mount Path Version BuildNumber
Server1 ROOT /dev/md2 / 2.0.0 32012
Server1 ALTROOT /dev/md1 /altroot 1.1.0 31340
The following example displays information about the root file-system partition named ROOT on a SpinServer named Server1:
spinserver::> system rootfilesystem show -ssid Server1 -name ROOT SpinServer ID Server1 Name ROOT Device /dev/md2 Mount Path / Version 2.0.0 BuildNumber 32012 InstallTime 10/24/2002-11:14:28 Last Sync Time UNKNOWN Last Config Sync Time UNKNOWN
CLI:
system rootfilesystem upgradesoftware -ssid spinserver -name file_system_name -installurl {cdrom | file://file_name | ftp://FTP_site}
GUI: Navigate to the System → Root File System node, then select the appropriate root file system from the table and run the Upgrade Software Release command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Upgrade Software Release.
The system rootfilesystem upgradesoftware command upgrades the SpinFS software on a SpinServer. See the Release Notes for instructions on upgrading to the latest version of SpinFS.
-ssid spinserver
This specifies SpinServer whose software is to be upgraded.
-name file_system_name
This specifies the root file-system partition on which the software upgrade is to be installed. Possible values are ROOT and ALTROOT.
-installurl {cdrom | file://file_name | ftp://FTP_site}
This specifies the location (CD-ROM, file, or FTP site) that contains the software upgrade. If cdrom is specified, the SpinServer automatically mounts and unmounts the CD-ROM as part of the upgrade process.
The following example upgrades the software on the ROOT partition of a SpinServer named Server1 from a CD-ROM.
spinserver::> system rootfilesystem upgradesoftware -ssid Server1 -name ROOT -installurl cdrom
CLI:
system software show [-ssid spinserver -name software_package_name]
GUI: Navigate to the System → Software Packages node. To display information about a specific software package, select it from the table and run the Show command from the drop-down menu of the action pane.
The system software show command displays the following information about the software packages installed on a SpinServer system:
SpinServer ID
Package name
Version number
Build number
Time and date of installation
Summary description
To obtain information about a specific software package installed on a specific SpinServer, use the -ssid and -name parameters. To obtain information about all software packages on all SpinServers in a cluster, issue the command without any parameters.
[-ssid spinserver]
This is the ID given to the SpinServer. This parameter is optional; however, if it is used, the -name parameter must also be specified.
[-name software_package_name]
This is name of the software package. This parameter is optional; however, if it is used, the -ssid parameter must also be specified.
The following example displays information about all software packages installed on a SpinServer:
spinserver::> system software show -ssid Server1 -name spinmgmt SpinServer ID Pkg Name Version Build Install Time Server1 spinfs 2.0.0 34917 12/19/02 2:40 PM Server1 spinrdb 2.0.0 34842p 12/18/02 9:02 AM Server1 spinvldb 2.0.0 34842p 12/18/02 9:02 AM Server1 kernel 2.2.17spinos 34842p 12/18/02 9:01 AM Server1 spinsyslogd 2.0.0 34842p 12/18/02 9:02 AM Server1 spinsnmp 2.0.0 34842p 12/18/02 9:02 AM Server1 modutils 2.4.2 5 12/5/01 6:41 AM Server1 spinmgmt 2.0.0 34842p 12/18/02 9:02 AM Server1 glibc 2.2.4 19.3 12/19/01 4:40 PM Server1 spindiags 2.0.0 34842p 12/18/02 9:01 AM Server1 spingcjlib 3.1.0 34842p 12/18/02 9:02 AM Server1 libstdc++ 2.96 81 12/5/01 6:41 AM Server1 spinndmpd 2.0.0 34842p 12/18/02 9:02 AM Server12 spinfs 2.0.0 34917 12/19/02 2:35 PM Server12 spindiags 2.0.0 34842p 12/18/02 9:01 AM Server12 spinsyslogd 2.0.0 34842p 12/18/02 9:02 AM Server12 spinmgmt 2.0.0 34842p 12/18/02 9:02 AM Server12 spingcjlib 3.1.0 34985p 12/26/02 2:08 PM Server12 kernel 2.2.17spinos 34842p 12/18/02 9:01 AM Server12 spinvldb 2.0.0 34842p 12/18/02 9:02 AM Server12 spinndmpd 2.0.0 34842p 12/18/02 9:02 AM -- Type 'q' to quit and any key to continue --
The following example displays information about the spinmgmt software package installed on a server named Server1:
spinserver::> system software show -ssid Server1 -name spinmgmt
SpinServer ID Server1
Pkg Name spinmgmt
Version 2.0.0
Build 34842p
Install Time 12/18/02 9:02 AM
Summary Spinnaker SpinServer Element Management
Server
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.